Inter-layer parameter liaison systems and methods

ABSTRACT

An exemplary method includes generating an access record associated with a data session provided by at least one access layer element over an access network, generating an application record associated with an application provided by at least one application layer element over the access network, transmitting data representative of a correlation parameter associated with application from the at least one application layer element to the at least one access layer element via an inter-layer liaison subsystem, and inserting the correlation parameter associated with application and received from the at least one application layer element via the inter-layer liaison subsystem in the access record. In some examples, the method further includes correlating the access record and the application record based on the correlation parameter associated with the application. Other exemplary inter-layer parameter liaison methods and systems are also disclosed.

BACKGROUND INFORMATION

Access networks provide many people and organizations with access to avariety of applications. For example, with the proliferation of wirelesscommunication networks such as mobile telephone networks, access tomobile communication applications (e.g., voice communication, e-mail,and messaging applications) and other applications has become widelyavailable.

Providers of access networks and applications made available over theaccess networks often charge for use of the access networks andapplications. Unfortunately, certain conventional access networks do nothave adequate technical capabilities to support all pricing structuresthat may be desirable to a provider. For example, with a conventionalaccess network, separate billing records may be generated for eachconnection to the network and for each application accessed via theaccess network. A billing department may be forced to use a complicatedand/or labor intensive process to attempt to link related billingrecords together to generate a bill in accordance with a providerpricing structure. In some cases, because of the complicated nature ofthis task and/or of a pricing structure, the billing department may notbe able to generate a bill that accounts for all chargeable usage of theaccess network and/or for one or more applications accessed via theaccess network.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate various embodiments and are a partof the specification. The illustrated embodiments are merely examplesand do not limit the scope of the disclosure. Throughout the drawings,identical or similar reference numbers designate identical or similarelements.

FIG. 1 illustrates an exemplary access network system.

FIG. 2 illustrates exemplary layers of a multi-layer access networkarchitecture.

FIG. 3 illustrates an exemplary inter-layer parameter liaison system.

FIG. 4 illustrates an exemplary access layer subsystem.

FIG. 5 illustrates an exemplary application layer subsystem.

FIG. 6 illustrates an exemplary inter-layer liaison subsystem.

FIG. 7 illustrates an exemplary correlation subsystem.

FIG. 8 illustrates an exemplary inter-layer parameter liaison method.

FIG. 9 illustrates an exemplary inter-layer parameter liaison data flow.

FIG. 10 illustrates an exemplary correlation of an access record and anapplication record.

FIG. 11 illustrates another exemplary inter-layer parameter liaisonmethod.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Exemplary inter-layer parameter liaison systems and methods aredescribed herein. As described below, the exemplary systems and methodsmay facilitate transmitting of one or more correlation parameters acrossdistinct layers of a multi-layer access network architecture via aninter-layer liaison subsystem. As used herein, a “correlation parameter”may include any parameter specific to a layer and that may betransmitted to another layer via the inter-layer liaison subsystem.Examples of correlation parameters are described further below.

Transmission of a correlation parameter across layers via theinter-layer liaison subsystem may facilitate one or more operations. Asan example, a correlation parameter received from a layer may be used inone or more operations (e.g., location-based operations, billingoperations, layer-specific operations, etc.) performed at another layer.As another example, transmission of a correlation parameter acrosslayers via the inter-layer liaison subsystem may facilitate one or morecorrelation operations, such as correlation of layer-specific recordsassociated with one or more services, data, and applications providedover distinct layers of an access network. Correlated records may beused in one or more operations such as one or more billing operations(e.g., generating a bill for one or more services, data, andapplications provided over distinct layers of an access network).Examples of operations that may utilize one or more correlationparameters are described in more detail further below.

Exemplary embodiments of inter-layer parameter liaison systems andmethods will now be described in more detail with reference to theaccompanying drawings.

FIG. 1 illustrates an exemplary access network system 100 (or simply“system 100”). As shown in FIG. 1, system 100 may include a providersubsystem 102 and an access device 104 communicatively connected to oneanother by way of a network 106.

Access device 104 may be associated with a user, who may utilize accessdevice 104 to access one or more applications, data, and/or servicesmade available by provider subsystem 102 over network 106. Access device104 may include any device capable of communicating with providersubsystem 102 and/or accessing applications, data, and/or services madeavailable by provider subsystem 102 over network 106. Access device 104may include, but is not limited to, a computing device, a communicationdevice (e.g., a telephone), a wireless computing device, a wirelesscommunication device (e.g., a mobile telephone), a personal digitalassistant, a vehicular computing and/or communication device, anavigation device, a set-top box, a media content processing device, agaming device, and any other device configured to access one or moreapplications, data, and/or services made available by provider subsystem102 over network 106.

Access device 104 and provider subsystem 102 may communicate overnetwork 106 using any communication platforms and technologies suitablefor transporting data and/or communication signals, including knowncommunication technologies, devices, media, and protocols supportive ofremote data communications, examples of which include, but are notlimited to, data transmission media, communications devices,Transmission Control Protocol (“TCP”), Internet Protocol (“IP”), FileTransfer Protocol (“FTP”), Telnet, Hypertext Transfer Protocol (“HTTP”),Hypertext Transfer Protocol Secure (“HTTPS”), Session InitiationProtocol (“SIP”), Simple Object Access Protocol (“SOAP”), ExtensibleMark-up Language (“XML”) and variations thereof, Simple Mail TransferProtocol (“SMTP”), Real-Time Transport Protocol (“RTP”), User DatagramProtocol (“UDP”), Global System for Mobile Communications (“GSM”)technologies (e.g., Long Term Evolution (“LTE”)), Code Division MultipleAccess (“CDMA”) technologies, Evolution Data Optimized Protocol (“EVDO”)(e.g., “1×EVDO”), Time Division Multiple Access (“TDMA”) technologies,Short Message Service (“SMS”), Multimedia Message Service (“MMS”), radiofrequency (“RF”) signaling technologies, radio transmission technologies(e.g., One Times Radio Transmission Technology (“1×RTT”)), wirelesscommunication technologies (e.g., Bluetooth, Wi-Fi, etc.), in-band andout-of-band signaling technologies, optical signaling technologies, andother suitable communications technologies.

Network 106 may include one or more networks, including, but not limitedto, access networks, wireless networks, mobile telephone networks (e.g.,cellular telephone networks), closed media networks, open medianetworks, subscriber television networks, closed communication networks,open communication networks, satellite networks, navigation networks,optical fiber networks (e.g., fiber-to-the-premises (“FTTP”) networks),broadband networks, narrowband networks, voice communications networks(e.g., VoIP networks), Public Switched Telephone Networks, the Internet,wide area networks, local area networks, public networks, privatenetworks, and any other networks capable of carrying data and/orcommunications signals between access device 104 and provider subsystem102. Communications between provider subsystem 102 and access device 104may be transported using any one of above-listed networks, or anycombination or sub-combination of the above-listed networks.

Multiple layers are typically used to support communications,applications, data, and services provided over network 106. For example,provider subsystem 102 and network 106 may be configured to providenetwork-based communications, applications, data, and services based ona layered communications and network protocol design, such as an OpenSystems Interconnection (“OSI”) reference model (or simply “OSI model”).The OSI model defines seven hierarchical layers—a physical layer, a datalink layer, a network layer, a transport layer, a session layer, apresentation layer, and an application layer. Each layer may include acollection of conceptually similar functions and computing hardwareand/or instructions (e.g., software) configured to perform thefunctions. The layers may be hierarchical such that one layer mayreceive data and/or services from an underlying layer and provide dataand/or services to a higher layer. For example, a layer may provide acommunication path that may be used by an application associated with ahigher layer. The OSI model illustrates one example of a multi-layerarchitecture that may be used to support communications, applications,data, and services provided over network 106. Any other suitablemulti-layer architecture may be used in other examples to supportcommunications, applications, data, and services provided over network106.

One drawback to a multi-layer architecture may be disconnects betweenlayers. While the layers may be hierarchical in nature and may utilizedata and or services provided by other layers, certain functionsassociated with specific layers may be separate and independent ofcertain functions associated with other layers.

FIG. 2 illustrates exemplary layers that may be used by providersubsystem 102 and/or network 106 to provide communications,applications, data, and/or services over network 106. FIG. 2 illustratestwo separate layers, namely an access layer 202 and an application layer204. This is illustrative only. The description of FIG. 2 may apply toadditional layers and/or any other layers of a multi-layer networkarchitecture used to support communications, applications, data, and/orservices provided over network 106.

As shown in FIG. 2, access layer 202 may include one or more accesslayer elements 206 (e.g., access layer elements 206-1 through 206-N) andapplication layer 204 may include one or more application layer elements208 (e.g., application layer elements 208-1 through 208-N). An accesslayer element 206 may include computing hardware and/or instructions(e.g., software) configured to provide one or more functions specific toaccess layer 202. An application layer element 208 may include computinghardware and/or instructions (e.g., software) configured to provide oneor more functions specific to application layer 204.

As described further below, there may be an inherent disconnect betweenone or more functions associated with application layer 204 and one ormore functions associated with access layer 202. For example, billingrecord functions may be separate and independent within each of thelayers 204 and 206. However, provider subsystem 102 may be configured tocorrelate inter-layer functions and/or data, including correlatingfunctions and/or data between access layer 202 and application layer204.

To illustrate, FIG. 3 is a block diagram of an exemplary inter-layerparameter liaison system 300 (or simply “system 300”). As shown in FIG.3, system 300 may include an access layer subsystem 302, applicationlayer subsystem 304, inter-layer liaison subsystem 306, and correlationsubsystem 308.

Subsystems 302, 304, 306, and 308 may include or be implemented on oneof more computing devices, including one or more computing deviceswithin provider subsystem 102 and/or network 106. For example, one ormore of the subsystems 302, 304, 306, and 308 may include or beimplemented on one or more of the access layer elements 206 and/orapplication layer elements 208 shown in FIG. 2. In certain embodiments,inter-layer liaison subsystem 306 may be implemented on a networkdevice, such as a policy server or a device including a database ofsubscriber information (e.g., a home location register), configured tocommunicate with one or more access layer elements 206 and one or moreapplication layer elements.

Exemplary components and functions of each of the subsystems 302, 304,306, and 308 will now be described.

FIG. 4 illustrates exemplary components of access layer subsystem 302.As shown in FIG. 4, access layer subsystem 302 may include acommunication facility 402, processing facility 404, storage facility406, and access facility 410 communicatively connected to one another.The facilities 402-410 may be communicatively connected using anysuitable technologies. Each of the facilities 402-410 may be implementedas hardware, computing instructions (e.g., software) tangibly embodiedon a computer-readable medium, or a combination of hardware andcomputing instructions configured to perform one or more of the accesslayer subsystem operations described herein.

Communication facility 402 may be configured to send and receivecommunications over network 106 (e.g., to/from access device 104) and/orto/from one or more other subsystems 304, 306, and 308. Communicationfacility 402 may include any device, logic, and/or other technologiessuitable for transmitting and receiving data and other communications.In certain embodiments, communication facility 402 may be configured tosupport network access communications over network 106. Communicationfacility 402 may be configured to interface with any suitablecommunication media, protocols, formats, platforms, and networks,including any of those mentioned herein.

Processing facility 404 may be configured to control, execute, and/ordirect execution of operations of one or more components of the accesslayer subsystem 302. Processing facility 404 may execute and/or directexecution of operations in accordance with computer-executableinstructions such as may be stored in data storage facility 406 or othercomputer-readable medium. As an example, processing facility 404 may beconfigured to process communications, including demodulating, decoding,and parsing received communications, and encoding and modulatingcommunications for transmission over network 106.

Data storage facility 406 may include one or more data storage media,devices, or configurations and may employ any type, form, andcombination of computer-readable media. For example, the data storagefacility 406 may include, but is not limited to, a hard drive, networkdrive, flash drive, magnetic disc, optical disc, random access memory(“RAM”), dynamic RAM (“DRAM”), other non-volatile and/or volatilestorage unit, or a combination or sub-combination thereof. Data may betemporarily and/or permanently stored in the data storage facility 406.

Access facility 410 may be configured to provide access services overnetwork 106. For example, access facility 410 may be configured toprovide (e.g., establish, maintain, terminate, and tear down) a datasession with access device 104 over network 106. As an example, accesslayer subsystem 302 may receive a request from access device 104 toestablish a data session over network 106. Access facility 410 maycontrol establishment of the requested data session with access device104. A data session may comprise any suitable connection sessionfacilitating communications between access device 104 and one or moreelements of provider subsystem 102 over network 106.

A data session may be specific to a particular type of communicationprotocol or technology supported over network 106. For example, a datasession may include, without limitation, an EVDO, LTE, 1×RTT, orsubscriber television based connection session.

Access facility 410 may be further configured to maintain access recorddata 412 associated with data sessions. As shown in FIG. 4, accessrecord data 412 may be stored in storage facility 406 of access layersubsystem 302. Access record data 412 may include one or more accessrecords associated with one or more data sessions provided, or beingprovided, by access facility 410. For example, when a data session isestablished with access device 104, access facility 410 may generate anaccess record associated with the data session (i.e., a “data sessionaccess record”). The access facility 410 may update the contents of thedata session access record based on events associated with the datasession, such as data being transmitted via the data session and/ortermination of the data session. Access facility 410 may maintain thecontents of the data session access record in at least substantiallyreal time.

A data session access record may include any information associated witha data session. For example, a data session access record may include,without limitation, information identifying an access layer element thatestablished the data session, information identifying one or more accesslayer elements that participated in providing the data session (e.g., anetwork node identifier for an access layer element), timestamps fortimes at which the data session was started and/or stopped, informationabout the access device 104 associated with the data session (e.g.,geographic location information such as a geographic area identifierindicating a geographic location of access device 104), informationabout origination and termination endpoint devices, information aboutthe length of time that a data session is active (e.g., duration inseconds and/or minutes of usage), data throughput associated with thedata session (e.g., kilobyte usage), information about data session type(e.g., information indicating an EVDO based data session), informationdelineating upstream and downstream data throughput via the datasession, and any other information descriptive of or otherwiseassociated with the data session.

Access facility 410 may be configured to generate one or morecorrelation parameters associated with a data session (i.e., “datasession correlation parameters”). As described herein, one or more datasession correlation parameters may be used in one or more operations,such as operations correlating an access record associated with a datasession with one or more related records associated with other layers(e.g., an application record associated with application layer 204).

A data session correlation parameter may include any data associatedwith a data session, including data that may be used to correlate anaccess record associated with the data session with one or more relatedrecords that are associated with other layers. For example, a datasession correlation parameter may include a data session identifierand/or a data session access record identifier that may be used toidentify the data session and/or the access record associated with thedata session.

As another example, a data session correlation parameter may include alocation parameter associated with a data session. The locationparameter may include location information indicating one or moregeographic locations, access layer elements 206, locations of accesslayer elements 206, and/or locations of access device 104 associatedwith the data session. For example, the location parameter may indicatea general geographic location of access device 104 when the data sessionis established, when the data session is terminated, when access to anapplication via the data session is initiated, and/or when access to anapplication via the data session is terminated. To this end, accessfacility 410 may be configured to determine one or more geographiclocations, access layer elements 206, locations of access layer elements206, and/or locations of access device 104 associated with the datasession and/or applications accessed via the data session.

The above-described examples of correlation parameters associated with adata session are illustrative only. A data session correlation parametermay include any parameter associated with a data session and/or specificto access layer 202. In other embodiments, other data sessioncorrelation parameters may be generated and transmitted to one or moreother layers via inter-layer liaison subsystem 306 for use in one ormore operations (e.g., for use in operations performed by an applicationlayer element 208 such as an application server or for use incorrelating an access record associated with a data session.)

One or more data session correlation parameters may be included in anaccess record associated with a data session. In certain embodiments,for example, access facility 410 may be configured to insert acorrelation parameter in a data session access record.

In certain examples, an access record associated with a data session maycomprise a billing record associated with the data session (i.e., “datasession billing record”). A data session billing record may include anyof the access record information described above, as well as any otherinformation about the data session that may be used for one or morebilling operations. In certain examples, a correlation parameterassociated with a data session, and which may be included in a datasession billing record, may comprise a billing identifier associatedwith the data session (i.e., a “data session billing identifier”).

Access layer subsystem 302 may be configured to transmit datarepresentative of one or more correlation parameters associated with adata session to application layer subsystem 304 via inter-layer liaisonsubsystem 306 for use by application layer subsystem 304 in one or moreapplication layer operations, including insertion of the correlationparameter(s) in one or more application records, as described furtherbelow.

In certain embodiments, access layer subsystem 302 may be furtherconfigured to provide data representative of a data session accessrecord to correlation subsystem 308 for use in one or more correlationoperations, as is also described further below. As is also describedfurther below, access layer subsystem 302 may be configured to receiveone or more correlation parameters associated with other layers (e.g.,an application correlation parameter associated with application layer204) and to use the received correlation parameter(s) in one or moreaccess layer operations, including insertion of the received correlationparameter(s) in an access record associated with a data session for usein correlating the data session access record with one or more relatedrecords associated with the other layers.

FIG. 5 illustrates exemplary components of application layer subsystem304. As shown in FIG. 5, application layer subsystem 304 may include acommunication facility 502, processing facility 504, storage facility506, and application facility 510 communicatively connected to oneanother. The facilities 502-510 may be communicatively connected usingany suitable technologies. Each of the facilities 502-510 may beimplemented as hardware, computing instructions (e.g., software)tangibly embodied on a computer-readable medium, or a combination ofhardware and computing instructions configured to perform one or more ofthe application layer subsystem operations described herein.

Communication facility 502 may be configured to send and receivecommunications over network 106 and/or to/from one or more othersubsystems 302, 306, and 308. Communication facility 502 may include anydevice, logic, and/or other technologies suitable for transmitting andreceiving data and other communications. In certain embodiments,communication facility 502 may be configured to supportapplication-related communications over network 106 (e.g., atapplication layer 204 of network 106). Communication facility 502 may beconfigured to interface with any suitable communication media,protocols, formats, platforms, and networks, including any of thosementioned herein.

Processing facility 504 may be configured to control, execute, and/ordirect execution of operations of one or more components of theapplication layer subsystem 304. Processing facility 504 may executeand/or direct execution of operations in accordance withcomputer-executable instructions such as may be stored in data storagefacility 506 or other computer-readable medium. As an example,processing facility 504 may be configured to process communications,including demodulating, decoding, and parsing received communications,and encoding and modulating communications for transmission over network106.

Data storage facility 506 may include one or more data storage media,devices, or configurations and may employ any type, form, andcombination of computer-readable media. For example, the data storagefacility 506 may include, but is not limited to, a hard drive, networkdrive, flash drive, magnetic disc, optical disc, random applicationmemory (“RAM”), dynamic RAM (“DRAM”), other non-volatile and/or volatilestorage unit, or a combination or sub-combination thereof. Data may betemporarily and/or permanently stored in the data storage facility 506.

Application facility 510 may be configured to provide one or moreapplications over network 106. As used herein, an “application” providedby application facility 510 of application layer subsystem 304 overnetwork 106 may include any application executable, function, service,and/or data provided over network 106 (e.g., to access device 104 vianetwork 106). Examples of such applications may include, but are notlimited to, voice communication service applications (e.g., cellulartelephone service applications and/or Voice over Internet Protocol(“VoIP”) service applications), location-based service applications(e.g., global positioning system (“GPS”) service applications), ringtoneapplications, text-messaging service applications (e.g., SMS),media-messaging service applications (e.g., MMS), e-mail serviceapplications, chat service applications, video delivery applications,audio delivery applications, multimedia delivery applications, contentdownload and/or streaming applications, conference call serviceapplications, data upload and storage applications, and data accessservice applications (e.g., web-access service applications).

In certain examples, applications provided over network may be providedvia a data session provided by access layer subsystem 302 as describedabove. For example, a data session between access device 104 and accesslayer subsystem 302 may be used to transport data associated with anapplication provided to the access device 104 by application layersubsystem 304. Hence, communications technologies used to establish thedata session, such as EVDO, 1×RTT, and LTE, may be used to deliver datafor applications provided by application layer subsystem 304 to accessdevice 104 via the data session. Accordingly, a user of access device104 (e.g., an end user such as a subscriber to one or more accessservices and/or applications) may obtain access to one or moreapplications provided by application layer subsystem 304 over network106.

For example, access facility 410 may establish a data session withaccess device 104 over network 106 as described above. Access device 104may then request an application be provided over the data session.Application facility 510 may receive the application request and providethe requested application to access device 104 via the data session.

Application facility 510 may be further configured to maintainapplication record data 512 associated with applications provided overnetwork 106. As shown in FIG. 5, application record data 512 may bestored in storage facility 506 of application layer subsystem 304.Application record data 512 may include one or more application recordsassociated with one or more applications provided, or being provided, byapplication facility 510. For example, when an application is providedto access device 104, application facility 510 may generate anapplication record associated with the application. The applicationfacility 510 may update the contents of the application record based onevents associated with the application, such as sending and/or receivingof application-related data by application facility 510. Applicationfacility 510 may maintain the contents of the application record in atleast substantially real time.

An application record may include any information associated with anapplication provided by application facility 510 over network 106. Forexample, an application record may include, without limitation,information identifying an application layer element that launchedand/or executed the application, information identifying one or moreapplication layer elements that participated in providing theapplication (e.g., a network node identifier for an application layerelement), timestamps for times at which the application was startedand/or stopped, information about the access device 104 associated withthe application (e.g., IP address information for the access device 104and/or geographic location information such as a geographic areaidentifier indicating a geographic location of access device 104),information about origination and termination endpoint elements and datacounts, information about the length of time that an application isactive (e.g., duration in seconds and/or minutes of usage), datathroughput associated with the application (e.g., kilobyte usage),information delineating upstream and downstream data throughput relatedto the application, and any other information descriptive of orotherwise associated with the application.

Application facility 510 may be configured to generate one or morecorrelation parameters associated with an application (i.e.,“application correlation parameters”). As described herein, one or moreapplication correlation parameters may be used in one or moreoperations, such as operations correlating an application recordassociated with an application with one or more related recordsassociated with other layers (e.g., a data session record associatedwith access layer 202).

An application correlation parameter may include any data associatedwith an application and/or specific to application layer 204, includingdata that may be used to correlate an application record associated withthe application with one or more related records that are associatedwith other layers. For example, an application correlation parameter mayinclude an application identifier and/or an application recordidentifier that may be used to identify the application and/or theapplication record associated with the application. These examples ofcorrelation parameters associated with an application are illustrativeonly. In other embodiments, other application correlation parameters maybe generated by application facility 510.

One or more application correlation parameters may be included in anapplication record associated with an application. In certainembodiments, for example, application facility 510 may be configured toinsert an application correlation parameter in an application record.

In certain examples, an application record associated with anapplication may comprise a billing record associated with theapplication (i.e., an “application billing record”). An applicationbilling record may include any of the application record informationdescribed above, as well as any other information about the applicationthat may be used for one or more billing operations. In certainexamples, a correlation parameter associated with an application, andwhich may be included in an application billing record, may comprise abilling identifier associated with the application (i.e., an“application billing identifier”).

Application layer subsystem 304 may be configured to transmit datarepresentative of one or more correlation parameters associated with anapplication to access layer subsystem 302 via inter-layer liaisonsubsystem 306 for use by access layer subsystem 302 in one or moreaccess layer operations, including insertion of the correlationparameter(s) in one or more asset records, as described further below.Application layer subsystem 304 may be further configured to providedata representative of an application record to correlation subsystem308 for use in one or more correlation operations, as is also describedfurther below.

As is also described further below, in certain embodiments applicationlayer subsystem 304 may be configured to receive one or more correlationparameters associated with other layers (e.g., a data sessioncorrelation parameter associated with access layer 202) and to use thereceived correlation parameter(s) in one or more application layeroperations, including insertion of the received correlation parameter(s)in an application record associated with an application. Examples ofother application layer operations are described further below. Incertain embodiments, the correlation parameter(s) may be used tocorrelate the application record with one or more related recordsassociated with the other layers and/or for other operations (e.g.,generating a bill for usage of an application), as described furtherbelow.

FIG. 6 illustrates exemplary components of inter-layer liaison subsystem306. As shown in FIG. 6, inter-layer liaison subsystem 306 may include acommunication facility 602, processing facility 604, storage facility606, and liaison facility 610 communicatively connected to one another.The facilities 602-610 may be communicatively connected using anysuitable technologies. Each of the facilities 602-610 may be implementedas hardware, computing instructions (e.g., software) tangibly embodiedon a computer-readable medium, or a combination of hardware andcomputing instructions configured to perform one or more of the accesslayer subsystem operations described herein.

Communication facility 602 may be configured to send and receivecommunications over network 106 and/or to/from one or more othersubsystems 302, 304, and 308. In particular, communication facility 602may be configured to support communications with multiple layers of amulti-layer architecture, including with access layer subsystem 302(e.g., with one or more access layer elements 206 of access layer 202)and with application layer subsystem 304 (e.g., with one or moreapplication layer elements 208 of application layer 204). Communicationfacility 602 may include any device, logic, and/or other technologiessuitable for transmitting and receiving data and other communications.Communication facility 602 may be configured to interface with anysuitable communication media, protocols, formats, platforms, layers, andnetworks, including any of those mentioned herein.

Processing facility 604 may be configured to control, execute, and/ordirect execution of operations of one or more components of theinter-layer liaison subsystem 306. Processing facility 604 may executeand/or direct execution of operations in accordance withcomputer-executable instructions such as may be stored in data storagefacility 606 or other computer-readable medium. As an example,processing facility 604 may be configured to process communications,including demodulating, decoding, converting, and/or parsing receivedcommunications, and encoding, modulating, and/or convertingcommunications for transmission over network 106 and/or for transmissionto one or more layers of a multi-layer network architecture.

Data storage facility 606 may include one or more data storage media,devices, or configurations and may employ any type, form, andcombination of computer-readable media. For example, the data storagefacility 606 may include, but is not limited to, a hard drive, networkdrive, flash drive, magnetic disc, optical disc, random access memory(“RAM”), dynamic RAM (“DRAM”), other non-volatile and/or volatilestorage unit, or a combination or sub-combination thereof. Data may betemporarily and/or permanently stored in the data storage facility 606.

Liaison facility 610 may be configured to function as an inter-layerparameter liaison. For instance, liaison facility 610 may be configuredto acquire and forward one or more correlation parameters betweenvarious layers of a multi-layer network architecture. As an example,liaison facility 610 may acquire data representative of a correlationparameter from a particular layer (e.g., from a layer element of a firstlayer) and forward data representative of the acquired correlationparameter to another layer (e.g., to a layer element of a second layer).In certain embodiments, correlation parameters may be acquired andforwarded in at least substantially real time by liaison facility 610.

To illustrate acquisition and forwarding of a correlation parameter,inter-layer liaison subsystem 306 may acquire data representative of acorrelation parameter associated with a data session from access layersubsystem 302 (e.g., from at least one access layer element 206).Inter-layer liaison subsystem 306 may then transmit (e.g., forward) datarepresentative of the acquired correlation parameter associated with thedata session to application layer subsystem 304 (e.g., to at least oneapplication layer element 208). Application layer subsystem 304 may usethe received correlation parameter in one or more application layeroperations such as insertion of the correlation parameter associatedwith the data session in an application record associated with anapplication that is related to the data session (e.g., an applicationthat is provided to access device 104 via the data session). The datasession correlation parameter may include any of the parametersdescribed above, including a data session identifier and/or locationparameter, for example.

Additionally or alternatively, inter-layer liaison subsystem 306 mayacquire data representative of a correlation parameter associated withan application from application layer subsystem 304 (e.g., from at leastone application layer element 208). Inter-layer liaison subsystem 306may then transmit (e.g., forward) data representative of the acquiredcorrelation parameter associated with the application to access layersubsystem 302 (e.g., to at least one access layer element 206). Accesslayer subsystem 302 may use the received correlation parameter in one ormore access layer operations such as insertion of the correlationparameter associated with the application in an access record associatedwith a data session that is related to the application (e.g., a datasession that is used to deliver the application to access device 104).The application correlation parameter may include any of the parametersdescribed above, including an application identifier, for example.

Liaison facility 610 may be further configured to maintain correlationparameter data 612 representative of one or more correlation parametersacquired and/or or transmitted by inter-layer liaison subsystem 306 asdescribed above. As shown in FIG. 6, correlation parameter data 612 maybe stored in storage facility 606 of inter-layer liaison subsystem 306.In certain embodiments, when a correlation parameter is acquired byinter-layer liaison subsystem 306, liaison facility 610 may store datarepresentative of the correlation parameter in the correlation parameterdata 612. In some examples, liaison facility 610 may maintain thecontents of the correlation parameter data 612 in at least substantiallyreal time. Inter-layer liaison subsystem 306 may provide correlationparameter data 612 to correlation subsystem 308 for use in correlatingrecords, as described below.

By functioning as an inter-layer parameter liaison, liaison facility610, and consequently inter-layer liaison subsystem 306, may beconfigured to bridge previous disconnects between certain functionsassociated with different layers of a multi-layer network architecture.Correlation parameters shared between multiple layers by inter-layerliaison subsystem 306 may be used for one or more purposes, including inone or more layer-specific operations, for automatically correlatingrelated records (e.g., an access record and one or more relatedapplication records), and/or for one or more billing operationsassociated with access services and applications provided over network106.

Examples of operations in which one or more correlation parameters thathave been transmitted across layers via inter-layer liaison subsystem306 may be used will now be described, including examples of using oneor more correlation parameters in correlating operations andlayer-specific operations (e.g., application-layer operations). Theseexamples are illustrative only. Correlation parameters that have beentransmitted across layers via inter-layer liaison subsystem 306 may beused in other operations in other embodiments.

To help illustrate an example of using one or more correlationparameters to correlate records across layers, FIG. 7 illustratesexemplary components of correlation subsystem 308. As shown in FIG. 7,correlation subsystem 308 may include a communication facility 702,processing facility 704, storage facility 706, input/output (“I/O”)facility 708, and correlation facility 710 communicatively connected toone another. The facilities 702-710 may be communicatively connectedusing any suitable technologies. Each of the facilities 702-710 may beimplemented as hardware, computing instructions (e.g., software)tangibly embodied on a computer-readable medium, or a combination ofhardware and computing instructions configured to perform one or more ofthe access layer subsystem operations described herein.

Communication facility 702 may be configured to send and receivecommunications over network 106 and/or to/from one or more othersubsystems 302, 304, and 306. In particular, communication facility 602may be configured to receive data representative of access records andapplication records from access layer subsystem 302 and applicationlayer subsystem 304, respectively. Communication facility 702 mayinclude any device, logic, and/or other technologies suitable fortransmitting and receiving data and other communications. Communicationfacility 702 may be configured to interface with any suitablecommunication media, protocols, formats, platforms, layers, andnetworks, including any of those mentioned herein.

Processing facility 704 may be configured to control, execute, and/ordirect execution of operations of one or more components of correlationsubsystem 308. Processing facility 704 may execute and/or directexecution of operations in accordance with computer-executableinstructions such as may be stored in data storage facility 706 or othercomputer-readable medium.

Data storage facility 706 may include one or more data storage media,devices, or configurations and may employ any type, form, andcombination of computer-readable media. For example, the data storagefacility 706 may include, but is not limited to, a hard drive, networkdrive, flash drive, magnetic disc, optical disc, random access memory(“RAM”), dynamic RAM (“DRAM”), other non-volatile and/or volatilestorage unit, or a combination or sub-combination thereof. Data may betemporarily and/or permanently stored in the data storage facility 706.

I/O facility 708 may be configured to receive user input and provideuser output and may include any hardware, firmware, software, orcombination thereof supportive of input and output capabilities. Forexample, I/O facility 708 may include one or more devices for capturinguser input, including, but not limited to, a microphone, keyboard orkeypad, touch screen component, scanner, camera, and receiver (e.g., anRF or infrared receiver).

I/O facility 708 may include one or more components for presenting datafor experiencing by a user 130, including, but not limited to, agraphics engine, a display, one or more display drivers, one or moreaudio speakers, and one or more audio drivers. Accordingly, I/O facility708 may present data and/or other content (e.g., access records,application records, bills, billing program tools) for experiencing bythe user 130.

Correlation facility 710 may be configured to correlate one or morerecords, including one or more access records and one or moreapplication records, based on at least one correlation parameter.Correlation of records may include correlation facility 710 identifyingrecords related to one another based on at least one shared correlationparameter and grouping the related records for processing as a group,such as in at least one billing operation (e.g., generating a bill for adata session and/or usage of one or more applications). In certainembodiments, correlation facility 710 may be configured to correlaterecords by automatically identifying a relationship between recordsbased on at least one shared correlation parameter included in therecords. This may include correlation facility 710 searching records forone or more correlation parameters. As an example, correlation facility710 may identify an access record and an application record as includingat least one shared correlation parameter (e.g., a data sessioncorrelation parameter and/or an application correlation parameter). Theaccess record and application record may share the correlation parameterdue to inter-layer liaison subsystem 306 acquiring and forwarding thecorrelation parameter across layers, and described above. Correlationfacility 710 may group the identified records together. For example,correlation facility 710 may group the access record and the applicationrecord together for use in subsequent operations (e.g., for use in atleast one billing operation).

Correlation subsystem 308 may be configured to perform one or morebilling operations. For instance, correlation subsystem 308 may beconfigured to utilize correlated records, such as a correlated accessrecord and application record, to generate a bill for access servicesand/or applications provided over network 106. As an example,correlation subsystem 308 may utilize a correlated access record andapplication record to generate a bill for a data session associated withthe access record and usage of an application associated with theapplication record. A specific example of such a billing operation isdescribed in more detail further below.

As shown in FIG. 7, access record data 412, application record data 512,and correlation parameter data 612 may be stored in storage facility 706of correlation subsystem 308. Correlation subsystem 308 may acquire theaccess record data 412, application record data 512, and correlationparameter data 612 from access layer subsystem 302, application layersubsystem 304, and inter-layer liaison subsystem 306, respectively.Correlation subsystem 308 may use the access record data 412,application record data 512, and/or correlation parameter data 612 forone or more of the correlation and/or billing operations describedherein. For example, correlation facility 710 may use correlationparameter data 612 to identify one or more correlation parameters to useto correlate access records and application records.

FIG. 8 illustrates an exemplary inter-layer liaison method 800. WhileFIG. 8 illustrates exemplary steps according to one embodiment, otherembodiments may omit, add to, reorder, and/or modify any of the stepsshown in FIG. 8. In certain embodiments, one or more of subsystems 302,304, 306, and 308 may perform one or more of the steps shown in FIG. 8.

In step 802, an access record associated with a data session provided byat least one access layer element over an access network is generated.For example, access layer subsystem 302 may generate the access recordfor the data session (e.g., when access layer subsystem 302 establishesthe data session over network 106).

In step 804, an application record associated with an applicationprovided by at least one application layer element over the accessnetwork is generated. For example, application layer subsystem 304 maygenerate the application record for the application (e.g., whenapplication layer subsystem 304 launches the application).

In step 806, data representative of a correlation parameter associatedwith the application is transmitted from the application layer elementto the access layer element via an inter-layer liaison subsystem 306.For example, application layer subsystem 304 may transmit datarepresentative of the application correlation parameter to inter-layerliaison subsystem 306, which may acquire and forward the applicationcorrelation parameter to access layer subsystem 302.

In step 808, data representative of a correlation parameter associatedwith the data session is transmitted from the access layer element tothe application layer element via the inter-layer liaison subsystem 306.For example, access layer subsystem 302 may transmit data representativeof the data session correlation parameter to inter-layer liaisonsubsystem 306, which may acquire and forward the application correlationparameter to access layer subsystem 302.

In step 810, the correlation parameter received from the applicationlayer element via the inter-layer liaison subsystem is inserted in theaccess record. For example, access layer subsystem 302 may insert thereceived application correlation parameter in the access record (e.g.,in a correlation parameter data field of the access record).

In step 812, the correlation parameter received from the access layerelement via the inter-layer liaison subsystem is inserted in theapplication record. For example, application layer subsystem 304 mayinsert the received data session correlation parameter in theapplication record (e.g., in a correlation parameter data field of theapplication record).

In step 814, the access record and the application record are correlatedbased on at least one of the correlation parameters. For example,correlation subsystem 308 may correlate the access record and theapplication record as described above based on the shared data sessioncorrelation parameter and/or application parameter.

FIG. 9 illustrates an exemplary inter-layer parameter liaison data flow900. Each arrow (e.g., arrows 902-1 through 902-8, collectively “arrows902”) shown in FIG. 9 is representative of a particular data flow. Itwill be recognized that the order in which illustrated data flows occurmay be rearranged, added to, or otherwise modified as may serve aparticular application. Moreover, it will be recognized that one or moreof the data flows shown in FIG. 9 may be performed concurrently.

As represented by data flow 902-1, access device 104 may transmit datarepresentative of a request to initiate a data session to access layerelement 206. The request may be initiated in any manner as may serve aparticular application. For example, the request may be initiated bypowering on or enabling a network connection of access device 104 suchthat access device 104 connects to access network 602. The data sessionmay include any of the exemplary data sessions described herein. Forexample, the data session may include an EVDO based communicationsession.

After the request to initiate a data session has been received by accesslayer element 206, access layer element 206 may create an access recordassociated with the data session. As described above, the access recordmay include, among other information, a correlation parameter associatedwith the data session (i.e., a data session correlation parameter). Asrepresented by data flow 902-2, data representative of the data sessioncorrelation parameter may be transmitted from access layer element 206to inter-layer liaison subsystem 306. Inter-layer liaison subsystem 306may be configured to temporarily store the data session correlationparameter for subsequent distribution to one or more application layerelements 208, as will be described below.

In response to the request to initiate a data session, access layerelement 206 may transmit data granting access to or otherwise associatedwith the data session to access device 104. This transmission of data isrepresented by data flow 902-3. Access device 104 may then utilize orotherwise access one or more data session functions.

During the data session, a user of access device 104 may desire toaccess an application provided by application layer element 208. Forexample, the user may desire to place a VoIP call, download a newringtone or other data, and/or access one or more location-basedservices. To this end, access device 104 may transmit datarepresentative of a request for the application to application layerelement 208. This request is represented by data flow 902-4.

In response, application layer element 208 may create an applicationrecord associated with the application. As described above, theapplication record may include a correlation parameter associated withthe application (i.e., an application correlation parameter). Asrepresented by data flow 902-5, application layer element 208 maytransmit data representative of the application correlation parameter tointer-layer liaison subsystem 306. Inter-layer liaison subsystem 306 maybe configured to temporarily store the application correlation parameterfor subsequent distribution to access layer element 206, as will bedescribed below.

Application layer element 208 may be further configured to transmit datagranting access to or otherwise associated with the application toaccess device 104. This transmission of data is represented by data flow902-6. Access device 104 may then utilize or otherwise access theapplication.

In some examples, inter-layer liaison subsystem 306 may transmit datarepresentative of the application correlation parameter to the accesslayer element 206, as represented by data flow 902-7. Likewise,inter-layer liaison subsystem 306 may transmit data representative ofthe data session correlation parameter to application layer element 208,as represented by data flow 902-8. In this manner, access layer element206 may receive and insert the application correlation parameter in theaccess record. Likewise, application layer element 208 may receive andinsert the data session correlation parameter in the application record.

In some examples, access layer element 206 and application layer element208 may be configured to transmit the access record and the applicationrecord, respectively, to correlation subsystem 308. Correlationsubsystem 308 may be configured to automatically identify the accessrecord and the application record as including the correlationparameters and group the access record and the application record forprocessing as a group. FIG. 10 illustrates an exemplary access record1000 and an exemplary application record 1002 and will be used todescribe an exemplary correlation of the access record 1000 and theapplication record 1002.

Access record 1000 may include information associated with a particulardata session. For illustrative purposes, the information shown in accessrecord 1000 corresponds to a data session initiated by access device104. Additional or alternative information associated with the datasession may be included in access record 1000 as may serve a particularapplication.

As shown in FIG. 10, access record 1000 may include identificationinformation 1004 associated with the data session. For example, accessrecord 1000 may include a billing record entity number (e.g., “PGW 3”)configured to identify the access record 1000 and/or an access layerelement 206 that generated the access record 1000 for one or morebilling purposes, a data session start date and time stamp (e.g., “Mar.10, 2009 8:37 AM”), a data session stop date and time stamp (e.g., “Mar.11, 2009 8:22 AM”), a mobile directory number (“MDN”) (e.g.,“9876543210”) configured to identify a telephone number associated withthe particular access device 104 used to initiate the data session, amobile station identification number (“MSID”) (e.g., “1234567890”)configured to identify a mobile station used to initiate the datasession, and an assigned IP address (e.g., “66.183.219.012”) configuredto identify an IP address of the access device 104 when the data sessionis initiated.

Access record 1000 may additionally or alternatively include one or moredata session correlation parameters 1006 associated with the datasession. For example, as shown in FIG. 10, access record 1000 mayinclude a data session billing identifier (e.g., “net123”) configured toidentify the data session for one or more billing operations and alocation parameter (e.g., “400131”) configured to indicate a geographiclocation of the access device 104 when the data session is initiated.

Access record 1000 may additionally or alternatively include one or moreapplication correlation parameters 1008 associated with one or moreapplications accessed by access device 104 during the data session. Forexample, access record 1000 may include an application billing parameter(e.g., “ap122”) associated with an application accessed by access device104. As described above, these application correlation parameters 1008may be transmitted to access layer element 206 from application layerelement 208 via inter-layer liaison subsystem 306 for insertion inaccess record 1000. In the example of FIG. 10, arrow 1022 illustratesthat application billing parameter “ap122” has been transmitted toaccess layer element 206 via inter-layer liaison subsystem 306 andinserted in access record 1000.

Access record 1000 may additionally or alternatively include usageinformation 1010 associated with the data session. For example, accessrecord 1000 may include a duration in seconds (“SOU”) (e.g., “85497”) ofthe data session, a duration in minutes (“MOU”) (e.g., “1425”), anamount of data in kilobytes (e.g., “10421”) received by access layerelement 206 from access device 104 during the data session, an amount ofdata in kilobytes (e.g., “513000”) sent by access layer element 206 toaccess device 104 during the data session, and a total number ofkilobytes of data sent and received (“KBU”) (e.g., “523421”) during thedata session.

Access record 1000 may additionally or alternatively include locationinformation 1012 corresponding to a geographic location of access device104 when the data session is initiated. Location data 1012 may be usedto generate the location parameter described above and may include asystem identification number (“SID”) (e.g., “40”) configured to identifya particular geographic market in which the access device 104 initiatedthe data session, a mobile switching center identification number(“MSCID”) (e.g., “1”) configured to identify the particular switch usedwithin the market by access device 104 to initiate the data session, anda cell identification number (e.g., “31”) configured to identify aparticular cell site used by access device 104 to initiate the datasession.

The information included within access record 1000 may be used bycorrelation subsystem 308 and/or any other component of providersubsystem 102 to track data usage and location-based informationassociated with the data session, perform one or more billing operationsassociated with the data session, and/or perform any other operation asmay serve a particular application. For example, identificationinformation 1004, correlation parameter information 1006 and 1008, usageinformation 1010, and/or location information 1012 may be compared toone or more limitations of a particular data access plan in order toappropriately bill a user for the data session.

Application record 1002 shown in FIG. 10 may include informationassociated with a particular application accessed by access device 104during the data session associated with access record 1000. Forillustrative purposes only, the information shown in application record1002 corresponds to a VoIP application used by access device 104 toplace a VoIP call during the data session associated with access record1000. It will be recognized that application record 1002 mayalternatively be associated with any other application as may serve aparticular application and that it may include any additional oralternative information associated with the application as may serve aparticular application.

The information included within application record 1002 may be used bycorrelation subsystem 308 and/or any other component of providersubsystem 102 to perform one or more billing operations associated withthe accessed application, track data usage associated with theapplication, and/or perform any other operation as may serve aparticular application.

As shown in FIG. 10, application record 1002 may include identificationinformation 1014 associated with the accessed application. For example,application record 1002 may include a billing record entity numberconfigured to identify the application record 1002 and/or an applicationlayer element 208 that generated the application record 1002 for one ormore billing purposes, an event start date and time stamp (e.g., “Mar.10, 2009 3:36 PM”, which may be a start date and time of a VoIP call),an event stop date and time stamp (e.g., “Mar. 10, 2009 4:00 PM”, whichmay be a stop date and time of the VoIP call), a mobile directory numberconfigured to identify a telephone number (e.g., “9876543210”)associated with the particular access device 104 used to place the VoIPcall, and an assigned IP address (e.g., “66.183.219.012”) configured toidentify an IP address of the access device 104 when the application isaccessed.

Application record 1002 may additionally or alternatively include one ormore of the data session correlation parameters 1006. As describedabove, these data session correlation parameters may be transmitted toapplication layer element 208 from access layer element 206 viainter-layer liaison subsystem 306 for insertion in application record1002. In the example of FIG. 10, arrow 1024 illustrates that datasession billing identifier “net123” has been transmitted to applicationlayer element 208 via inter-layer liaison subsystem 306 and inserted inapplication record 1002.

Application record 1002 may additionally or alternatively include anapplication correlation parameter 1008 (e.g., application billingparameter “ap122”). Application correlation parameter 1008 may begenerated by application layer element 208 as described above.

Application record 1002 may additionally or alternatively include alocation parameter 1016 (e.g., “400132”) configured to identify ageographic location of the access device 104 when the application isaccessed and location information 1018. Location information 1018 may beused to generate location parameter 1016 and may include a SID (e.g.,“40”) configured to identify a particular geographic market in which theaccess device 104 accessed the application, a MSCID (e.g., “1”)configured to identify the particular switch used within the market byaccess device 104 to access the application, and a cell identificationnumber (e.g., “32”) configured to identify a particular cell site usedby access device 104 to access the application.

It will be recognized that application layer element 208 may not becapable of determining all or a part of location information 1018.Hence, in some examples, access layer element 206 may be configured todetermine location information 1018 and location parameter 1016 andtransmit this data to application layer element 208 via inter-layerliaison subsystem 306 as one or more data session correlationparameters.

Application record 1002 may additionally or alternatively include usageinformation 1020. For example, application record 1002 may include aduration in seconds (e.g., “1440”) and minutes (e.g., “24”) of how longthe access device 104 utilizes the application (e.g., a duration of aVoIP call) and an amount of data (e.g., “4000”) associated with theapplication that is received and transmitted while the application isused by access device 104.

As described above, one or more data session correlation parameters maybe transmitted from an access layer element 206 to an application layerelement 208 via inter-layer liaison subsystem 306 for insertion inapplication record 1002. For example, as illustrated by arrow 1004 inFIG. 10, an access network correlation parameter “net123” has beeninserted in application record 1002.

In some examples, correlation subsystem 308 may be configured toautomatically identify access record 1000 and application record 1002 asincluding shared correlation parameters 1006,1008, and/or 1016 and groupaccess record 1000 and application record 1002 for use in at least onecorrelation operation. For example, access record 1000 and applicationrecord 1002 may be grouped for use in a billing operation.

For example, correlation subsystem 308 may be configured to correlateaccess record 1000 and application record 1002 such that an accuratebill for the data session associated with access record 1000 and forusage of the application associated with application record 1002 isgenerated. To illustrate, a user may have a data access plan thatcharges the user a certain amount of money for each kilobyte of datatransmitted during a data session associated with access record 1000.The user may be allowed to access an application associated withapplication record 1002 during the data session at a separate and/oradditional cost.

However, data associated with the application may be transmitted betweenaccess device 104 and application layer element 208 via the data sessionwhen the application is accessed. To avoid double-billing the user, thisdata associated with the application should not be included in theamount of data transmitted during the data session for which the userwill be billed. Hence, correlation subsystem 308 may be configured tosubtract the transmitted data associated with the application from thetotal transmitted data associated with the data session and bill theuser for the difference. In the example of FIG. 10, correlationsubsystem 308 may be configured to subtract 4000 kilobytes from 523421kilobytes and only bill the user for 519421 kilobytes of data usageunder the data access plan. The usage of the application may be billedas a separate charge (e.g., a fixed monthly fee).

Correlation subsystem 308 may additionally or alternatively beconfigured to detect differences in the location information 1012 and1018 included within access record 1000 and application record 1002,respectively, and to use the location information to generate anaccurate bill for the data session and for usage of the application.

For example, a user may initiate the data session associated with accessrecord 1000 at a particular location (e.g., San Francisco). While stillwithin the data session, the user may move to a new location (e.g.,Oakland) and access the application associated with application record1002 at the new location. The new location may have different accessfees, regulatory fees, taxes, and other costs associated with accessingthe application than the original location. By detecting this change inlocation, correlation subsystem 308 may be configured to generate a billfor the accessed application based on the fees associated with the newlocation.

FIG. 11 illustrates another exemplary inter-layer liaison method 1100.While FIG. 11 illustrates exemplary steps according to one embodiment,other embodiments may omit, add to, reorder, and/or modify any of thesteps shown in FIG. 11. In certain embodiments, one or more ofsubsystems 302, 304, 306, and 308 may perform one or more of the stepsshown in FIG. 11.

In step 1102, a correlation parameter is generated within a layer of amulti-layer network architecture. The correlation parameter may begenerated in any of the ways described herein. For example, thecorrelation parameter may be generated within access layer 202 or anyother layer of a multi-layer network architecture.

In step 1104, data representative of the correlation parameter istransmitted from the layer to at least one other layer of themulti-layer network architecture via an inter-layer liaison subsystem.Data representative of the correlation parameter may be transmitted fromthe layer to at least one other layer via the inter-layer liaisonsubsystem in any of the ways described herein. As an example, datarepresentative of the correlation parameter may be transmitted fromaccess layer 202 to application layer 204. This illustrative only. Thecorrelation parameter may be transmitted across any layers of amulti-layer network architecture.

In step 1106, the correlation parameter is used in at least oneoperation specific to the at least one other layer. The operation mayinclude any of the operations described herein.

To illustrate, an access layer element 206 within access layer 202 maytransmit a correlation parameter comprising a location parameterrepresentative of a geographic location of access device 104 to anapplication layer element 208 within application layer 204 viainter-layer liaison subsystem 306. Application layer element 208 may beconfigured to perform one or more location-based operations inaccordance with the location parameter. For example, application layerelement 208 may include a coupon server or other real-time advertisingserver configured to automatically transmit local coupons oradvertisements to access device 104. The coupons or advertisements maybe location-specific and selected in accordance with the locationparameter.

The operations described herein are merely illustrative of the manydifferent operations that may utilize one or more correlationparameters. Additional or alternative operations may include, but arenot limited to, fraud detection operations, troubleshooting operations,location-based emergency operations (e.g., E911 operations),access-device-specific operations, and/or any other operation specificto a particular layer as may serve a particular application.

In some examples, one or more of the exemplary systems or componentsthereof described herein may include or be implemented in any computinghardware and/or instructions (e.g., software programs), or combinationsof computing instructions and hardware, configured to perform one ormore of the processes described herein. In particular, it should beunderstood that the exemplary systems, or one or more components of theexemplary systems, may be implemented on one physical computing deviceor may be implemented on more than one physical computing device.Accordingly, the exemplary systems may include any one of a number ofcomputing devices employing any of a number of computer operatingsystems.

One or more of the processes described herein may be implemented atleast in part as computer-executable instructions, i.e., instructionsexecutable by one or more computing devices, tangibly embodied in acomputer-readable medium. In general, a processor (e.g., amicroprocessor) receives instructions, from a computer-readable medium(e.g., from a memory, etc.), and executes those instructions, therebyperforming one or more processes, including one or more of the processesdescribed herein. Such instructions may be stored and transmitted usinga variety of known computer-readable media.

A computer-readable medium (also referred to as a processor-readablemedium) includes any medium that participates in providing data (e.g.,instructions) that may be read by a computer (e.g., by a processor of acomputer). Such a medium may take many forms, including, but not limitedto, non-volatile media and/or volatile media. Non-volatile media mayinclude, for example, optical or magnetic disks and other persistentmemory. Volatile media may include, for example, dynamic random accessmemory (“DRAM”), which typically constitutes a main memory. Common formsof computer-readable media include, for example, a floppy disk, aflexible disk, hard disk, magnetic tape, any other magnetic medium, aCD-ROM, DVD, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, a RAM, a PROM, an EPROM, aFLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computing device can read.

Accordingly, each of the components of the exemplary systems describedherein may be implemented as hardware, computing instructions (e.g.,software) tangibly embodied on a computer-readable medium, or acombination of hardware and tangibly embodied computing instructionsconfigured to perform one or more of the processes described herein.

In the preceding description, various exemplary embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe scope of the invention as set forth in the claims that follow. Forexample, certain features of one embodiment described herein may becombined with or substituted for features of another embodimentdescribed herein. The description and drawings are accordingly to beregarded in an illustrative rather than a restrictive sense.

1. A method comprising: generating an access record associated with adata session provided by at least one access layer element over anaccess network; generating an application record associated with anapplication provided by at least one application layer element over theaccess network; transmitting data representative of a correlationparameter associated with application from the at least one applicationlayer element to the at least one access layer element via aninter-layer liaison subsystem; and inserting the correlation parameterassociated with the application and received from the at least oneapplication layer element via the inter-layer liaison subsystem in theaccess record.
 2. The method of claim 1, further comprising:transmitting data representative of a correlation parameter associatedwith the data session from the at least one access layer element to theat least one application layer element via the inter-layer liaisonsubsystem; and inserting the correlation parameter associated with thedata session and received from the at least one access layer element viathe inter-layer liaison subsystem in the application record.
 3. Themethod of claim 1, further comprising correlating the access record andthe application record based on the correlation parameter associatedwith the application.
 4. The method of claim 3, wherein the correlatingof the access record and the application record based on the correlationparameter comprises: automatically identifying the access record and theapplication record as including the correlation parameter associatedwith the application; and grouping the access record and the applicationrecord for use in at least one billing operation.
 5. The method of claim3, further comprising utilizing the correlated access record andapplication record to generate a bill for the data session and usage ofthe application.
 6. The method of claim 1, wherein the transmitting ofdata representative of the correlation parameter associated with theapplication from the at least one application layer element to the atleast one access layer element via the inter-layer liaison subsystemcomprises: acquiring with the inter-layer liaison subsystem the datarepresentative of the correlation parameter associated with theapplication from the at least one application layer element; andtransmitting with the inter-layer liaison subsystem data representativeof the acquired correlation parameter associated with the application tothe at least one access layer element.
 7. The method of claim 1, whereinthe transmitting of data representative of the correlation parameterassociated with the application from the at least one application layerelement to the at least one access layer element via the inter-layerliaison subsystem is performed in at least substantially real time. 8.The method of claim 1, tangibly embodied as computer-executableinstructions on at least one computer-readable medium.
 9. A methodcomprising: generating an access record associated with a data sessionprovided by at least one access layer element over an access network;generating an application record associated with an application providedby at least one application layer element over the access network;transmitting data representative of a correlation parameter associatedwith the data session from the at least one access layer element to theat least one application layer element via an inter-layer liaisonsubsystem; and inserting the correlation parameter associated with thedata session and received from the at least one access layer element viathe inter-layer liaison subsystem in the application record.
 10. Themethod of claim 9, further comprising: transmitting data representativeof a correlation parameter associated with the application from the atleast one application layer element to the at least one access layerelement via an inter-layer liaison subsystem; and inserting thecorrelation parameter associated with the application and received fromthe at least one application layer element via the inter-layer liaisonsubsystem in the access record.
 11. The method of claim 9, furthercomprising correlating the access record and the application recordbased on the correlation parameter associated with the data session. 12.The method of claim 11, wherein the correlating of the access record andthe application record based on the correlation parameter associatedwith the data session comprises: automatically identifying the accessrecord and the application record as including the correlation parameterassociated with the data session; and grouping the access record and theapplication record for use in at least one billing operation.
 13. Themethod of claim 11, further comprising utilizing the correlated accessrecord and application record to generate a bill for the data sessionand usage of the application.
 14. The method of claim 9, wherein thetransmitting of data representative of the correlation parameterassociated with the data session from the at least one access layerelement to the at least one application layer element via theinter-layer liaison subsystem comprises: acquiring with the inter-layerliaison subsystem the data representative of the correlation parameterassociated with the data session from the at least one access layerelement; and transmitting with the inter-layer liaison subsystem datarepresentative of the acquired correlation parameter associated with thedata session to the at least one application layer element.
 15. Themethod of claim 9, wherein the transmitting of data representative ofthe correlation parameter associated with the data session from the atleast one access layer element to the at least one application layerelement via the inter-layer liaison subsystem is performed in at leastsubstantially real time.
 16. The method of claim 9, tangibly embodied ascomputer-executable instructions on at least one computer-readablemedium.
 17. A method comprising: generating a correlation parameterwithin a layer of a multi-layer network architecture; transmitting datarepresentative of the correlation parameter from the layer to a at leastone other layer of the multi-layer network architecture via aninter-layer liaison subsystem; and using the correlation parameter in atleast one operation specific to the at least one other layer.
 18. Themethod of claim 17, wherein the correlation parameter comprises alocation parameter representative of a geographic location of an accessdevice.
 19. A system comprising: an access layer subsystem configured toprovide a data session with an access device, and generate an accessrecord for the data session, the access record including a data sessioncorrelation parameter associated with the data session; an applicationlayer subsystem configured to provide at least one application to theaccess device via the data session, and generate an application recordfor the application, the application record including an applicationcorrelation parameter associated with the application; an inter-layerliaison subsystem configured to communicate with the access layersubsystem and the application layer subsystem and to acquire datarepresentative of the application correlation parameter from theapplication layer subsystem, transmit data representative of theapplication correlation parameter acquired from the application layersubsystem to the access layer subsystem for insertion in the accessrecord, acquire data representative of the data session correlationparameter from the access layer subsystem, and transmit datarepresentative of the data session correlation parameter acquired fromthe access layer subsystem to the application layer subsystem forinsertion in the application record; and a correlation subsystemconfigured to correlate the access record and the application recordbased on at least one of the application correlation parameter and thedata session correlation parameter included in the access record and theapplication record.
 20. The system of claim 19, wherein the applicationcomprises at least one of a voice-communication service application, avoice-over-internet-protocol service application, a location-basedservice application, a ringtone application, a text-messaging serviceapplication, a media-messaging service application, an e-mail serviceapplication, and a chat service application, and a web-access serviceapplication.
 21. The system of claim 19, wherein: the application recordcomprises a billing record for usage of the application; and the accessrecord comprises a billing record for the data session.
 22. The systemof claim 21, wherein the correlation subsystem is further configured toutilize the correlated billing records to generate a bill based on datasession throughput and usage of the application.
 23. The system of claim19, wherein the inter-layer liaison subsystem is implemented on one ofan access layer element of an access layer and an application layerelement of an application layer.
 24. A system comprising: at least oneaccess layer element configured to provide a data session with an accessdevice and to generate a data session billing record for the datasession, the data session billing record including a data sessionbilling identifier; at least one application layer element configured toprovide at least one application to the access device via the datasession and to generate an application billing record for theapplication, the application billing record including an applicationbilling identifier; an inter-layer liaison subsystem configured tocommunicate with the at least one access layer element and the at leastone application layer element and to acquire the data session billingidentifier from the at least one access layer element, transmit the datasession billing identifier to the at least one application layer elementfor insertion in the application billing record, acquire the applicationbilling identifier from the at least one application layer element, andtransmit the application billing identifier to the at least one accesslayer element for insertion in the data session billing record.
 25. Thesystem of claim 24, further comprising a correlation subsystemconfigured to correlate the data session billing record and theapplication billing record based on at least one of the applicationbilling identifier and the data session billing identifier included inthe data session billing record and the application billing record.